home *** CD-ROM | disk | FTP | other *** search
- Path: cosy.sbg.ac.at!not-for-mail
- From: gwesp@dodo.cosy.sbg.ac.at (Gerhard Wesp)
- Newsgroups: comp.sys.cbm,comp.sys.atari.8bit
- Subject: Re: GNU C-compiler port to 6502
- Date: 1 Apr 1996 12:37:11 +0200
- Organization: Dept. of CS, University of Salzburg
- Message-ID: <4jobkn$6gh@dodo.cosy.sbg.ac.at>
- References: <4irqpb$7pc@esel.cosy.sbg.ac.at> <4jbmcf$733@news.iastate.edu> <4jgc70$lmt@dodo.cosy.sbg.ac.at> <4ji1te$dnk@agate.berkeley.edu>
- NNTP-Posting-Host: dodo.cosy.sbg.ac.at
-
- In article <4ji1te$dnk@agate.berkeley.edu>,
- Eric J. Korpela <korpela@islay.ssl.berkeley.edu> wrote:
- :
- >A native 6502 compiler could do that kind of optimization, our "macro"
- >compiler couldn't without an additional optimizer. My guess is that the
- >optimizer would be as hard to write as a native 6502 C compiler.
- :
- This is a tough example indeed. I don't know how to avoid such things
- except by having a good optimizer brush up the assembly code _after_
- the macro expansion has taken place. But, as you write, such an optimizer
- would be quite a lot of hard work to write.
-
- Well, the manual says that gcc is a 32 bit compiler... Perhaps it would
- really be better to try to make a ``true'' 6502 compiler (i.e. one which
- knows everything about the internals of the processor)? However, the
- ATARI cc65 results are a bit disappointing...
-
- Greetings,
- -Gerhard
-